Side-by-Side Installation

ProStructures 2023 supports side-by-side installation of multiple versions of ProStructures on the same machine. You can run multiple versions of ProStructures CONNECT Edition & ProStructures 2023 at the same time. Installation of ProStructures 2023 will by default occur alongside any of the previous installations. Removing previous versions of ProStructures will require a manual uninstall. ProStructures 2023's installation directory and Configuration are in a different location than the previous version. In the default installation, you can work on two different configurations defined during ProStructures CONNECT Edition and ProStructures 2023 installation. The application version naming FAQ describing major and minor releases is located here. [Bentley Lifecycle Policy | Bentley Systems | Infrastructure Engineering Software Company]

Note: As with all previous versions, the configuration is version specific. Two or more side-by-side installs cannot share a common configuration. If there is content (dataset or WorkSet files) you wish to carry forward into the newly installed version, you must follow the guidance for migrating and upgrading datasets and WorkSets. Once upgraded all users should use the same version of the application on a WorkSet.

Default Installation Path

ProStructures 2023 uses the same installation pattern for its major components as in previous versions, however, it includes the release year as a differentiator to allow side-by-side installs to take place.

Default Preference Folder Path

A preference folder for each installed version is created. You can copy some of the preference content from older to new versions post-installation. The preference folders are indicated using the Major version number in this case *"23"* "C:\Users\Common\AppData\Local\Bentley\ProStructures".

Set the Custom Configuration directory during Installation

Care and consideration should be given to instances where network configurations or ProjectWise managed workspaces are employed. You should create new configurations that are from the existing previous versions of the software. Following the pattern established above by clearly indicating the version or year in paths for clarity and differentiation.